@stof why was this merged? There's no way of having an interface that enforces a non-public method. It makes no sense to me.

@guilhermeblanco consistency

@Ocramius still doesn't make sense... I'm gonna quote PHP.net: http://php.net/interface

All methods declared in an interface must be public, this is the nature of an interface.

I just don't see the need of adding public. Even PHP manual does that... a bit weird to me.

It's just for the sake of having visibility everywhere all the time

It's actually a CS issue. I'd rather not put public all over my interfaces, but CS checkers are whiny about that.

@guilhermeblanco Check that even in the php.net interface example have the explicity visibility as public defined.
This also help IDEs generating the implementation methods with the right visibility and this is required by PSR-2.

@guilhermeblanco Following PSR-2